Draft
Conversation
…ofile=4c16g rep=1
…ofile=4c16g rep=1
…ofile=8c32g rep=1
…ofile=8c32g rep=1
…ofile=16c64g rep=1
…ofile=4c16g rep=1
…ofile=4c16g rep=1
…ofile=8c32g rep=1
…ofile=8c32g rep=1
…ofile=16c64g rep=1
…ofile=16c64g rep=1
…ofile=31c64g rep=1
Replace old benchmark-specific labels (fireactions-bench-pr2483, fireactions-highperf, fireactions-highmem, fireactions-standard, fireactions-low) with production 2-tier pool labels (fireactions-heavy, fireactions-light). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Temporary change to route Contract E2E tests to an isolated AX102 runner (1×8c64g) for benchmarking. Will revert after collecting timing data. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Test B: 16c128g isolated benchmark on AX102. Retries reduced to 1 to avoid wasting 3x time on the known flaky pure-proxy test. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- try-runtime.yml: all 3 jobs now use fireactions-tryruntime label (3×8c64g on AX102, dedicated Ryzen 9 7950X for IPC advantage) - contract-tests.yml: reverted to fireactions-heavy label and restored 3 retries after isolated AX102 benchmarking complete Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Finney gets dedicated 16c64g runner on AX102, devnet/testnet share 2×4c32g runners. Prioritizes finney (longest job) while keeping total vCPU at 24 (same as before, just redistributed). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Remove redundant linux, x64, and fireactions labels from runs-on blocks. All fireactions-heavy/light/tryruntime runners already have these labels, so specifying them adds no filtering value. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
benchmarking purposes only - not for merging